Skip to content

feat(composer): drafts survive restart, ↑ recall, Enter-to-send option, batched review comments (#1493 B) - #1496

Merged
currentbits merged 4 commits into
mainfrom
coder/1493-b-composer-durability-batched-revie-17fb0b
Oct 6, 2026
Merged

currentbits merged 4 commits into
mainfrom
coder/1493-b-composer-durability-batched-revie-17fb0b

Conversation

@currentbits

Copy link
Copy Markdown
Owner

Item B of #1493.

What changed

  1. Drafts survive a restart. Text, attachments (stored as paths, never image data), paste cards and review chips are saved per thread to localStorage, debounced and also flushed on unload, then restored on launch and cleared on send.
    • One storage key, capped at 1 MB in total. Over the cap, the largest paste cards are dropped first, then the ↑ history; text and attachments are always kept.
    • Drafts of deleted threads are pruned on idle.
  2. ↑ recall. ↑ in an empty composer recalls the last prompt sent on this thread; ↑/↓ step through the last 20 while the recalled text is unedited. The slash and mention popups keep their arrows, and a non-empty draft is left alone.
  3. Send-key setting. Settings › General › Display gets "Send with Enter (⇧ Enter for a new line)". It's opt-in: today's default (Enter = new line, ⌘/Ctrl+Enter = send) is unchanged. The keyboard sheet follows the setting and lists ↑ recall.
  4. Batched review comments. A gutter comment in Changes no longer starts a run. It becomes a draft chip (src/a.ts:L12-18 comment) that can be edited or removed. ⇧-click extends a comment to a range within one hunk. All chips go out with the typed text as one prompt.

Verified independently

🤖 Generated with Claude Code

Willem and others added 4 commits October 6, 2026 15:14
…start

Drafts mirror to localStorage per thread (debounced, size-capped: the
largest paste cards drop first), restore at load, clear on send, and are
pruned on idle for threads that no longer exist. Issue #1493 B.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Per-thread history of sent prompt text (capped at 20, persisted with the
draft). ↑/↓ walk it while the recalled text is untouched; popups and
multi-line drafts keep their arrows. Issue #1493 B.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings > General > Display gains "Send with Enter" (off by default,
so ⌘/Ctrl+Enter stays the send chord). With it on, bare Enter sends and
⇧Enter is the newline. The keyboard sheet follows the preference and
lists ↑ recall. Issue #1493 B.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A Git pane line comment no longer starts a run. It lands in the composer
as a chip (file:L12-18 plus the comment), editable and removable, and
every pending chip goes out as one prompt with the typed text on the next
send. ⇧-click extends a comment over a line range inside a hunk. Chips
persist with the draft. Issue #1493 B.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-06T13:35:41.353885Z c566cb5 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant